Confluent Platform End of Life (EOL) Dates & Support Timeline

Confluent Platform lifecycle status — the real story

Confluent Platform is Confluent's self-managed distribution of Apache Kafka, and each minor release ships with one Kafka version (Confluent Platform 8.3 carries Kafka 4.3, 7.9 carries Kafka 3.9). Confluent publishes a release date and up to three end-of-support dates per minor release on its Supported Versions and Interoperability page: one for Confluent Community software, one for Confluent Enterprise Standard support and one for Confluent Enterprise Platinum support. The page defines the tiers: "Standard support means any support level below Platinum support. For example, if you have Gold support, you have Standard support." It also states that "End of support is extended one year for Platinum support agreements" and that "The end of support date applies to minor versions and any maintenance versions that come after the minor version".

Starting with Confluent Platform 8.0, the support periods differ by licence. The page says Confluent Community software follows the Kafka community's "about one year of patch support", Standard support runs two years from the minor release, and Platinum runs three, so Confluent Platform 8.0 (June 11, 2025) has Community support to June 11, 2026, Standard support to June 11, 2027 and Platinum support to June 11, 2028. For 7.x releases, Community and Standard end on the same day, two years after release. Confluent also says it "removes packages and repository metadata for versions that reach end of life", so an installer or playbook that pins an end-of-life release can stop working once Confluent removes its packages.

Field mapping: support is the Confluent Community software end-of-support date (for 6.1 to 7.5, which the page dates for Standard and Platinum only, it is the Standard date). eol is the Confluent Enterprise Standard end-of-support date, the end of support for every customer below Platinum. extendedSupport is the Platinum end-of-support date: Confluent Platinum support (paid support tier) covers each release for one more year. Lines 6.1 to 7.5 have left the current page, so their dates come from the same page in the Confluent Platform 7.6 documentation. The latest patch in each line comes from the page's patch-version table and from Confluent's package archive. CISA's Known Exploited Vulnerabilities catalog (2026.10.08) has no Confluent entry.

Confluent Platform release and support pattern

Across the 16 release lines with a published release date, Confluent Platform has shipped a new line roughly every 4 months (median interval). A line typically stays in standard support for about 2 years from its release to its standard-support end date.

Of the 16 release lines tracked, 10 are past end of life and 6 are still within support. The newest line, 8.3, was released June 17, 2026. The next scheduled end of life is 7.8 on December 2, 2026 — 53 days from this build. The longest-supported line currently published is 8.3, to June 17, 2028. Upstream also publishes an extended-support phase for 16 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Confluent Platform end of life mean for your organization?

When a version of Confluent Platform reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Confluent Platform should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Confluent Platform reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Confluent Platform versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products